|
|
|
|
|
|
|
and deleting services, configuring services, determining their dependencies, and setting service security. A fully implemented set of classes would include these features. |
|
|
|
|
|
|
|
|
Interaction with other tools. The utility creates a reference list of the current state of each service when it loads. If you start or stop a service using another tool, such as the Control Panel, the utility will not see that change or update its internal list. This means that, if you restore the original values using the utility, the values will not reflect changes made after the application loaded. |
|
|
|
|
|
|
|
|
Reentrant version. The current version of the utility disables all user input while it is trying to start or stop a service. This is necessary to prevent reentrancy problemsfor example, an attempt to stop a service while it is being started. A more sophisticated program could manage multiple start and restore operations, preventing such conflicts through a smarter algorithm. Whether it is worth the effort to develop that functionality is up to you. |
|
|
|
|
|
|
|
|
Isn't that the way it always works out? You go to the trouble of creating a useful little utility and it's obsolete before you even use it! Actually, it will continue to be useful for those of you using Active Server Pages and for other applications where you wish to start or stop services. And there is a lot to learn from the example. As for meI'm going to be writing Web classes using Visual Basic 6. |
|
|
|
|
|